-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📖 Refactor InfraMachine contract #11223
📖 Refactor InfraMachine contract #11223
Conversation
|
||
Among those rules: | ||
- InfraMachine MUST report a [provider ID](../../providers/contracts/infra-machine.md#inframachine-provider-id) for the Machine | ||
- InfraMachine SHOULD define a [failure domain](../../providers/contracts/infra-machine.md#inframachine-failure-domain) where machines should be placed in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- InfraMachine SHOULD define a [failure domain](../../providers/contracts/infra-machine.md#inframachine-failure-domain) where machines should be placed in | |
- InfraMachine SHOULD define a [failure domain](../../providers/contracts/infra-machine.md#inframachine-failure-domain) field that decides where machines are placed in |
Maybe. Sould define a failureDomain sounds a bit unclear
Otherwise it sounds like the InfraMachine comes up with the failureDomain, but I think it's the other way around
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went through the rabbit hole about failure domains management, and discovered that since 1.3.0 we are supporting a two ways contract for compatibility reason/for allowing a transparent transition from when there was no failure domain support in Cluster API and InfraMachine was authoritative WRT to failure domain placement
I updated the doc to reflect current state, and also added a proposal for cleaning up tech debt with v1beta2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If what I'm proposing is ok, I'm going to open an issue to track this + brings this up in the office hours
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general sounds good to me.
I assume we still have use cases going forward where no failureDomain is specified in Machine, then the infra provider just picks one and we want to surface that back?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
868ccf0
to
76b3db0
Compare
76b3db0
to
de9897b
Compare
/lgtm /hold |
LGTM label has been added. Git tree hash: bcb0b8a6c19ad5699c20de58165a29079018c4f9
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
What this PR does / why we need it:
This PR refactor the InfraMachine contract. Most notably
/area documentation